i18n-ja-release-8.5: translate doc changes from pingcap/docs release-8.5 on 2026-09-17 - #23900

EN source is identical across all 8 ai/guides/*-with-pytidb.md files
for these bullet-list labels, but the JA sync produced inconsistent
renderings per file. Unify to a single form in each case:

- "Source Code" -> "ソースコード" (translated label), link text ->
  "GitHub で見る" (majority form)
- "A {{{ .starter }}} instance" -> "{{{ .starter }}} インスタンス"
  (translated, matching existing majority precedent)
- "OpenAI API key" / "Jina AI API key" -> "OpenAI APIキー" /
  "Jina AI APIキー", matching the katakana convention used elsewhere
  in the repo (e.g. Datadog APIキー, TiDB Cloud APIキー)
- "Text-to-image search" / "Image-to-image search" (capability
  description, not literal UI text) -> translated to match the
  file's own already-translated summary line

Also add missing trailing newlines to the touched files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Translate bare "Vector Search" to "ベクトル検索" throughout the body
(title, headings, prose, and link text), matching the corpus-wide
convention already used elsewhere. Also normalize "TiDB Vector
Search" to "TiDBベクトル検索" to match the settled rendering used in
19 other files (e.g. ai-feature-concepts.md, dev-guide-vector-search.md).

Left untouched:
- The image alt text on line 48, matching the existing literal-alt-text
  precedent (e.g. "Process Schematic" in dashboard-ops-deploy.md)
- The "[Vector data types]" / "[Vector search index]" link texts,
  which are different terms tied to their own target pages

Also add the missing trailing newline.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…ew.md

- "[Vector data types]" / "[Vector search index]" -> match the H1
  headings of their target pages: "ベクトルデータ型" and
  "ベクトル検索インデックス"
- "[distance function]" -> "距離関数", matching the existing rendering
  in releases/release-8.4.0.md for a link to the same page
- "embedding とも呼ばれます" -> "単に埋め込みとも呼ばれます": the
  English word was redundant since 埋め込み is already the
  established JA rendering of "embedding" used throughout this file

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"API コントラクト" is an unprecedented, unnatural rendering of "API
contract" with zero other occurrences in the corpus. Use "API 仕様",
matching the established "OpenAPI仕様" convention used throughout the
repo for this kind of interface-specification concept.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…i/ti/

The MT sync left the English nouns "mount"/"unmount" untranslated in
prose across ~17 files in ai/ti/, while the verb forms in the very
same sentences were already correctly rendered as マウント/アンマウント.
Convert the noun forms to マウント/アンマウント to match, following the
established repo-wide convention (マウントオプション, マウントパス, etc.)
Code fences, inline code spans, link URLs, and heading anchors are
left untouched, including literal CLI command/flag names such as
`mount-file-system` and `--mount-path`.

Also, in manage-filesystem-layers.md:
- "checkpoint mount" -> "チェックポイントマウント", matching this
  file's own majority use of チェックポイント in its title and headings
- bare "fork" -> "フォーク", matching the well-established rendering
  used throughout the rest of the corpus (e.g. CONTRIBUTING.md)

Also add missing trailing newlines to the touched files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same class of defect as the earlier mount/unmount sweep: the MT sync
left the English noun "token"/"tokens" untranslated in prose across
33 files in ai/ti/, while the established convention already used
トークン extensively elsewhere in this same directory (e.g.
manage-filesystem-tokens.md).

Skips: fenced code blocks, inline code spans, link URLs, heading
anchors, and any "token" adjacent to a hyphen (protects literal CLI
command names like `ti fs delete-file-system-token` and compound
terms like `token-management`). One hyphenated non-CLI instance
("owner-token") was manually normalized to match this file's own
"owner token" usage before the sweep would apply.

Also add missing trailing newlines to the touched files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"Choose one outcome for a layer" was translated as "choose a result",
but 結果 (result/consequence) isn't something you choose beforehand —
what follows are two concrete operations (rollback or commit). Use
操作 (operation) instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…ion section

In manage-filesystem-layers.md's "move local state to another
machine" section, translate the terms that already have an
established rendering elsewhere in this same corpus:
- overlay directory/root -> オーバーレイディレクトリ/オーバーレイルート
  (matches ti-fs-unpack-file-system.md's own "ローカルオーバーレイルート")
- archive path -> アーカイブパス, cache -> キャッシュ, pack (verb) ->
  パック(します) (all well-established elsewhere in ai/ti/)
- restore (verb) -> 復元する (matches ti-fs-create-layer.md's "レイヤーを復元できます")

Left as-is: "write-back" (no katakana equivalent exists anywhere in
the corpus; it's tied to the literal --write-back-cache flag), and
"pack と unpack" in the sentence that immediately precedes links to
the literal pack-file-system/unpack-file-system command references
(unpack has no katakana precedent anywhere, so translating only
"pack" here would read as more inconsistent, not less).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same class of defect as the mount/token sweeps: the MT sync left the
English noun "owner" untranslated in prose across most of ai/ti/,
while オーナー was already used for the identical concept (owner
token, owner FS token, owner access) in a handful of other files
(e.g. manage-filesystem-vault-secrets.md, ti-fs-vault-mount-vault.md).

Skips: fenced code blocks, inline code spans, link URLs, heading
anchors, and any "owner" adjacent to a hyphen. One hyphenated
instance ("owner-only file") was manually translated to "オーナー専用
ファイル" instead of being left bare.

Also add missing trailing newlines to the touched files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"Companion state and mount locators" was translated using a native
word (付随, "attached/accompanying"), but "companion" refers to the
specific ti-drive9 background runtime component and stays literal
English everywhere else in this file and across ai/ti/ (companion
runtime, companion home, companion-home). Keep it literal here too
for consistency.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"scoped" and "owner" name the two token kinds in the TiDB Cloud
Filesystem token system, and オーナー was already unified for the
latter. For the same consistency, translate "scoped" to スコープ付き,
matching the existing (if minority) precedent in
ti-parallel-agent-dataset-example.md and
ti-fs-list-file-system-tokens.md.

Skips: fenced code blocks, inline code spans, and any "scoped"
adjacent to a hyphen (the literal `generate-file-system-scoped-token`
command name stays untouched).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same class of defect as mount/unset: the verb form is already
consistently translated (委任する, 13+ occurrences), and the
adjectival "delegated X" form even has existing precedent using the
same native rendering (委任された vault トークン, 委任されたフィールド
in ti-vault-agent-secrets-example.md), but 8 more prose occurrences
were left as bare English. Unify them to 委任された rather than
introducing a new katakana loanword.

Skips: fenced code blocks and inline code spans (e.g. the "# Read the
delegated token ..." bash comments stay untouched).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"新しい認可済み操作は防止されます" literally reads as "new
already-authorized operations are prevented", which is
self-contradictory (an already-authorized operation wouldn't need
preventing). The EN source means revocation stops new operations from
being authorized going forward. Rephrase to match.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"secret"/"secrets" is translated to シークレット 7 other times in this
same file; this one instance was left bare English. Keep "Vault"
literal, matching its consistent use elsewhere as part of the
"TiDB Cloud Filesystem Vault" feature name.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"hydration"/"hydrate" stays literal English everywhere else across
ai/ti/ (25+ occurrences in 6 files, including mixed constructions
like "hydrate する"/"hydrate している"). This one katakana instance in
ti-overview.md was an isolated outlier, and "ハイドレーション" risks
being read as the skincare/moisture term rather than the Git-object
sense intended here. Revert to match the dominant convention.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…ention

"dirty" has broad, well-established katakana precedent across the
TiDB docs corpus (dirty read/write isolation levels, dirty page
cache, dirty data), including within ai/ti/ itself
(ti-fs-drain-file-system.md's "ダーティハンドル"). This one instance was
left as bare English.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…unt-filesystem.md

- "durability barrier" -> 耐久性バリア, matching
  ti-regions-security-and-limitations.md's own description of the
  same drain-file-system concept ("FUSE 専用のオンライン耐久性バリア")
- "layer checkpoint" -> レイヤーのチェックポイント, matching the phrasing
  in manage-filesystem-layers.md ("レイヤーのチェックポイントを作成する前に")

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…tem.md

"device、capability、security、および environment" summarizes the
docker run flags shown just above (--device, --cap-add,
--security-opt, --env) in plain descriptive prose, not literal code.
Translate to デバイス、ケーパビリティ、セキュリティ、および環境変数.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…ai/ti/

Found 8 more prose occurrences of bare "overlay" beyond the one the
user flagged in mount-filesystem.md, across ti-filesystem.md,
ti-fs-mount-file-system.md, and ti-fs-unmount-file-system.md. Unify
all of them to オーバーレイ, matching the dominant convention already
established across ai/ti/ (オーバーレイルート, オーバーレイディレクトリ,
etc.). Skips CLI flags, code, and literal file paths like
"local-overlay.tar.gz".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…ology

Checked the live labs.tidb.io Japanese UI (landing page and in-lab
step panel for this exact lab, demo_901): "Lab" is consistently
rendered as 演習 throughout (nav "実践演習", exercise cards, sidebars),
and no "Lab Guide" label appears anywhere in the actual product UI.
Translate accordingly instead of leaving it as literal English.

The linked title "TiDB Cloud Filesystem for Agent Sandbox Lab" stays
literal, matching the corpus-wide convention for lab/resource link
titles elsewhere (e.g. the <ResourceCard title="..."> instances).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…h.md

EN uses a symmetric "Pre-filtering"/"Post-filtering" pair, but this file
rendered them asymmetrically: 事前フィルタリング (kanji) paired with
ポストフィルタリング (katakana). Sibling files
vector-search-full-text-search-{sql,python}.md already use a matched
kanji pair, 事前フィルタリング/事後フィルタリング, for the same SQL
compatibility bullet. Unify vector-search.md's 6 occurrences of
ポストフィルタリング to 事後フィルタリング to match. Anchor
{#post-filtering} is unchanged.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

リコール率 (katakana) was a lone outlier against the established
再現率 rendering used elsewhere in the ai/ corpus for the same ML/IR
metric (vector-search.md's "recall", vector-search-index.md's
"recall rate").

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Matches the no-space katakana-compound convention used elsewhere in
the same file (line 34's ベクトルインデックスアルゴリズム).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Both sites left "layer ID" untranslated, inconsistent with the
established レイヤー ID rendering used at 7 other sites across
ai/ti/reference/ (e.g. ti-fs-fork-layer.md's near-identical
"returned layer ID" sentence).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"companion" stays literal English (established corpus convention),
but "access" is a normal translatable word, as shown by this same
file's own heading directly above ("## アクセスをチェックする").
Leaving the whole compound in English was inconsistent with that.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same-file self-contradiction: the preceding line already translates
"mount profile" to マウントプロファイル, but this line left the
anaphoric "profile" reference as literal English.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same-paragraph self-contradiction: "journal entries" two sentences
later already translates to ジャーナルエントリ, and 5 sibling files
(ti-fs-journal-*.md, ti-cli-reference.md) all use "Filesystem
ジャーナル" consistently.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…n cross-reference audit

Found via a systematic audit of every internal markdown link across
the PR's ~190 files, comparing link text against each target's actual
JA title/heading:

- ai/_index.md, ai/guides/vector-search-hybrid-search.md: unify
  リランキング/ランキング変更 to 再ランキング, matching reranking.md's
  own H1 and TOC-ai.md's existing usage. Also fixed a dropped を
  particle before ご覧ください.
- ai/ti/reference/ti-fs-fork-layer.md: translate "[tag reference]"
  to タグ参照, matching sibling ti-fs-delete-layer.md's rendering of
  the same recurring EN phrase.
- ai/ti/reference/ti-db-list-db-clusters.md: translate "[TiDB Cloud
  API v1beta1 Overview]" to match Japanese convention.
- ai/ti/reference/ti-filesystem-vault.md, ti-install-configure-update.md:
  unify シークレット to Secrets (English) in link text, matching the
  target guide's own title "...Vault Secrets を管理する" and this
  same file's other reference to it.
- ai/ti/reference/ti-filesystem.md: unify プロバイダー to Providers
  (English) in link text, matching the target guide's own title
  "...AI Providers を設定する".
- ai/ti/reference/ti-migrate-from-tdc.md, ai/ti/ti-overview.md:
  translate residual English link text ("[Install TiDB Cloud CLI]",
  "[Quick Start]") to match their Japanese target titles.
- ai/ti/ti-overview.md: unify 日常的な to 日次の to match
  ti-daily-workflow-example.md's own title (EN uses the identical
  string "Run a Daily TiDB Cloud CLI Workflow" for both).
- ai/ti/guides/ti-parallel-agent-dataset-example.md: translate
  residual "subject" to サブジェクト, matching 3 sibling files.
- Also fixed 2 pre-existing missing-EOF-newline files touched above
  (ti-filesystem-vault.md, ti-overview.md).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same-file self-contradiction: line 31 already translates "Global
preferences" to グローバル設定, and the file's own title uses 設定
for the same concept, but this line left "preferences" as literal
English.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

EN lists 4 items ("profiles, credentials, preferences, and Filesystem
state"), but JA had 5, translating "preferences" twice: once as 設定
and once left as literal "Preferences". Remove the duplicate.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

This file's near-duplicate access-mode/role table used 想定される用途
while the identical table in ti-configuration-and-credentials.md uses
the more concise 想定用途, which better fits a table header (a noun
phrase, matching sibling headers like "TiDB Cloud built-in role").

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Bare "actor" is already established as アクター at 4 other sites
(ti-fs-journal-*.md), but "Actor ID" was left literal in these 2
sibling option descriptions.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"file", "upload", "Git workspace API", "Journal", "fork", "event",
and "token-management" were left literal, inconsistent with
established renderings used elsewhere in ai/ti/ (a near-parallel
operation list in ti-regions-security-and-limitations.md already
translates the same set: ファイル操作、レイヤー、マウント、
Git ワークスペース、ジャーナル、および Vault 操作). "Vault", "SQL",
and `chmod` correctly stay as-is (established literal terms/code).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"flush" is established as フラッシュ at 10+ sites across ai/ti/, and
"file system" (generic sense) is already translated to ファイルシステム
earlier in this same file (line 55's --file-system-id option).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Bare prose "stdout" is established as 標準出力 at 4 sites elsewhere
in ai/ti/ (flag names like --to-stdout correctly stay literal as
code identifiers, but this was prose, not a flag reference).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same-file self-contradiction: 3 other sentences in this file already
translate "refresh" to 更新, but this warning's opening word was left
as literal English.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Both terms are established as シェル履歴 and プロセス一覧 at 5 other
sites across ai/ti/ (manage-filesystem-vault-secrets.md,
ti-vault-agent-secrets-example.md, ti-configuration-and-credentials.md,
ti-install-configure-update.md, ti-regions-security-and-limitations.md).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Established elsewhere in ai/ti/: pack -> パック
(ti-fs-pack-file-system.md), pack path -> パックパス
(ti-filesystem.md's 自動パックパス), archive path -> アーカイブパス
(manage-filesystem-layers.md). "unpack" intentionally stays literal
per an earlier session decision to avoid colliding with 復元/restore.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

…patible

The near-identical sibling option in
ti-fs-update-file-system-extract-configuration.md already translates
this to "プロバイダーベース URL", and "OpenAI-compatible" is
established as "OpenAI 互換" at 7+ other sites in ai/ti/.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Same-file inconsistency after the previous commit fixed the sibling
option's OpenAI-compatible wording; this remaining prose sentence
still had it as literal English mixed with な.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Sibling sentences in configure-filesystem-ai-providers.md and
ti-fs-vault-mount-vault.md already translate the identical
"read and export ... without placing it in shell history" prose to
エクスポート. The literal `export TI_FS_AI_PROVIDER_API_KEY` shell
command below is unaffected (correctly stays as code).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"label" and "hint" are each independently established as ラベル and
ヒント at many sites in ai/ti/. "grant" correctly stays literal,
matching this file's own consistent convention for that term.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

"tier" in the TiDB Cloud cluster-tier sense is established as プラン
corpus-wide, matching tidb-cloud/select-cluster-tier.md's own title
"プランを選択してください".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Prose (not backtick-quoted as a literal API value in EN), unlike the
correctly-literal `permission denied` API response value elsewhere in
ai/ti/. 権限拒否 matches existing corpus precedent in
check-before-deployment.md, and completes the parallel 3-item symptom
list (the other two items are already translated noun phrases).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

ai/_index.md had a same-file split: "Start here" rendered as
開始はこちら (1 table) vs まずはこちら (2 tables) — unify to the
majority まずはこちら.

Also found a 3rd rendering of the "Run a Daily TiDB Cloud CLI
Workflow" link text (毎日の, in ai/_index.md) beyond the
日常的な/日次の split fixed earlier this session, plus a leftover
日常的な in TOC-ai.md that the earlier fix missed. Unify all to
日次の, matching ti-daily-workflow-example.md's own title.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>